Pattern Notebook

http://downlode.org/etext/patterns/index.html Overview of the pattern Language from "The Timeless Way of Building"

http://c2.com/cgi/wiki?AliArsanjani Ali Arsanjani on Ward's Wiki

http://guides.brucejmack.net/Pattern Documents/DesignPatterns/Misc/invoice_architecture.htm

Cross domain patterns are the hardest to see because they are clouded by domain specific terminology. The following version is from EventHelix so it's from a real-time communications point of view. Good object definition usually come from a good metaphor or even better when the objects align with reality. This establishes the roles and responsibilities of the object. A good example is using the Publish-Subscribe Design Pattern for a one to many notification system. As designs evolve into the actual solution the separation between the roles and responsibilities lessens.